Skip to content

[CLEANUP] Avoid multiline strings in OutputFormatTest - #1429

Merged
JakeQZ merged 1 commit into
mainfrom
cleanup/multiline-in-outputformattest
Dec 14, 2025
Merged

[CLEANUP] Avoid multiline strings in OutputFormatTest#1429
JakeQZ merged 1 commit into
mainfrom
cleanup/multiline-in-outputformattest

Conversation

@oliverklee

Copy link
Copy Markdown
Collaborator

Also avoid literal tabs.

@oliverklee
oliverklee force-pushed the cleanup/multiline-in-outputformattest branch from 779193d to 69887d7 Compare December 14, 2025 20:17
@oliverklee oliverklee changed the title [CLEANUP] Avoid multiple strings in OutputFormatTest [CLEANUP] Avoid multiline strings in OutputFormatTest Dec 14, 2025
@coveralls

coveralls commented Dec 14, 2025

Copy link
Copy Markdown

Coverage Status

coverage: 69.027%. remained the same
when pulling 69887d7 on cleanup/multiline-in-outputformattest
into 704c17f on main.

self::assertSame(
'.main, .test {font: italic normal bold 16px/1.2 "Helvetica",Verdana,sans-serif;background: white;}
@media screen {.main {background-size: 100% 100%;font-size: 1.3em;background-color: #fff;}}',
".main, .test {font: italic normal bold 16px/1.2 \"Helvetica\",Verdana,sans-serif;background: white;}\n"

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's debatable whether such a string should be single-quoted, with "\n" concatenated. Either way is fine I think.

@JakeQZ
JakeQZ merged commit 539c64c into main Dec 14, 2025
23 checks passed
@JakeQZ
JakeQZ deleted the cleanup/multiline-in-outputformattest branch December 14, 2025 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants